IRIX Base Documentation 2001 May/SGI IRIX Base Documentation 2001 May.iso/usr/share/catman/p_man/cat3/libelf/elf_begin.z/elf_begin

Text File | 1998-10-30 | 28.2 KB | 330 lines

EEEELLLLFFFF____BBBBEEEEGGGGIIIINNNN((((3333EEEE))))                                                    EEEELLLLFFFF____BBBBEEEEGGGGIIIINNNN((((3333EEEE))))



NNNNAAAAMMMMEEEE
     _eeee_llll_ffff______bbbb_eeee_gggg_iiii_nnnn - make a file descriptor

SSSSYYYYNNNNOOOOPPPPSSSSIIIISSSS
     _cccc_cccc [_f_l_a_g ...] _f_i_l_e ...  _----_llll_eeee_llll_ffff [_l_i_b_r_a_r_y ...]

     _####_iiii_nnnn_cccc_llll_uuuu_dddd_eeee _<<<<_llll_iiii_bbbb_eeee_llll_ffff_...._hhhh_>>>>
     _EEEE_llll_ffff _****_eeee_llll_ffff______bbbb_eeee_gggg_iiii_nnnn_((((_iiii_nnnn_tttt _ffff_iiii_llll_dddd_eeee_ssss_,,,, _EEEE_llll_ffff______CCCC_mmmm_dddd _cccc_mmmm_dddd_,,,, _EEEE_llll_ffff _****_rrrr_eeee_ffff_))))_;;;;

DDDDEEEESSSSCCCCRRRRIIIIPPPPTTTTIIIIOOOONNNN
     _eeee_llll_ffff______bbbb_eeee_gggg_iiii_nnnn, _eeee_llll_ffff______nnnn_eeee_xxxx_tttt, _eeee_llll_ffff______rrrr_aaaa_nnnn_dddd, and _eeee_llll_ffff______eeee_nnnn_dddd work together to process ELF
     object files, either individually or as members of archives.  After
     obtaining an ELF descriptor from _eeee_llll_ffff______bbbb_eeee_gggg_iiii_nnnn, the program may read an
     existing file, update an existing file, or create a new file.  _f_i_l_d_e_s is
     an open file descriptor that _eeee_llll_ffff______bbbb_eeee_gggg_iiii_nnnn uses for reading or writing.  The
     initial file offset [see _llll_ssss_eeee_eeee_kkkk(2)] is unconstrained, and the resulting
     file offset is undefined.

     _c_m_d may have the following values.

     _EEEE_LLLL_FFFF______CCCC______NNNN_UUUU_LLLL_LLLL      When a program sets _c_m_d to this value, _eeee_llll_ffff______bbbb_eeee_gggg_iiii_nnnn returns
                     a null pointer, without opening a new descriptor.  _r_e_f is
                     ignored for this command.  See _eeee_llll_ffff______nnnn_eeee_xxxx_tttt(3E) and the
                     examples below for more information.

     _EEEE_LLLL_FFFF______CCCC______RRRR_EEEE_AAAA_DDDD      When a program wishes to examine the contents of an
                     existing file, it should set _c_m_d to this value.
                     Depending on the value of _r_e_f, this command examines
                     archive members or entire files.  Three cases can occur.

                     First, if _r_e_f is a null pointer, _eeee_llll_ffff______bbbb_eeee_gggg_iiii_nnnn allocates a
                     new ELF descriptor and prepares to process the entire
                     file.  If the file being read is an archive, _eeee_llll_ffff______bbbb_eeee_gggg_iiii_nnnn
                     also prepares the resulting descriptor to examine the
                     initial archive member on the next call to _eeee_llll_ffff______bbbb_eeee_gggg_iiii_nnnn, as
                     if the program had used _eeee_llll_ffff______nnnn_eeee_xxxx_tttt or _eeee_llll_ffff______rrrr_aaaa_nnnn_dddd to ``move''
                     to the initial member.

                     Second, if _r_e_f is a non-null descriptor associated with
                     an archive file, _eeee_llll_ffff______bbbb_eeee_gggg_iiii_nnnn lets a program obtain a
                     separate ELF descriptor associated with an individual
                     member.  The program should have used _eeee_llll_ffff______nnnn_eeee_xxxx_tttt or
                     _eeee_llll_ffff______rrrr_aaaa_nnnn_dddd to position _r_e_f appropriately (except for the
                     initial member, which _eeee_llll_ffff______bbbb_eeee_gggg_iiii_nnnn prepares; see the example
                     below).  In this case, _f_i_l_d_e_s should be the same file
                     descriptor used for the parent archive.

                     Finally, if _r_e_f is a non-null ELF descriptor that is not
                     an archive, _eeee_llll_ffff______bbbb_eeee_gggg_iiii_nnnn increments the number of
                     activations for the descriptor and returns _r_e_f, without
                     allocating a new descriptor and without changing the
                     descriptor's read/write permissions.  To terminate the


                                                                        PPPPaaaaggggeeee 1111






EEEELLLLFFFF____BBBBEEEEGGGGIIIINNNN((((3333EEEE))))                                                    EEEELLLLFFFF____BBBBEEEEGGGGIIIINNNN((((3333EEEE))))



                     descriptor for _r_e_f, the program must call _eeee_llll_ffff______eeee_nnnn_dddd once
                     for each activation.  See _eeee_llll_ffff______nnnn_eeee_xxxx_tttt(3E) and the examples
                     below for more information.

     _EEEE_LLLL_FFFF______CCCC______RRRR_EEEE_AAAA_DDDD______MMMM_MMMM_AAAA_PPPP This command duplicates the actions of _EEEE_LLLL_FFFF______CCCC______RRRR_EEEE_AAAA_DDDD but
                     uses the _mmmm_mmmm_aaaa_pppp() system call to access the file data in a
                     more memory efficient manner.  If, after _l_i_b_e_l_f has
                     opened the file, another process truncates the file
                     _l_i_b_e_l_f could get a Segmentation Violation attempting to
                     read data it believes is in the file (but which is no
                     longer there due to the truncation).  Applications
                     calling _l_i_b_e_l_f with _EEEE_LLLL_FFFF______CCCC______RRRR_EEEE_AAAA_DDDD______MMMM_MMMM_AAAA_PPPP may therefore wish to
                     install a signal handler for _SSSS_IIII_GGGG_SSSS_EEEE_GGGG_VVVV (Segmentation
                     Violation) and issue a message when it happens.

     _EEEE_LLLL_FFFF______CCCC______RRRR_DDDD_WWWW_RRRR      This command duplicates the actions of _EEEE_LLLL_FFFF______CCCC______RRRR_EEEE_AAAA_DDDD and
                     additionally allows the program to update the file image
                     [see _eeee_llll_ffff______uuuu_pppp_dddd_aaaa_tttt_eeee(3E)].  That is, using _EEEE_LLLL_FFFF______CCCC______RRRR_EEEE_AAAA_DDDD gives a
                     read-only view of the file, while _EEEE_LLLL_FFFF______CCCC______RRRR_DDDD_WWWW_RRRR lets the
                     program read _a_n_d write the file.  _EEEE_LLLL_FFFF______CCCC______RRRR_DDDD_WWWW_RRRR is not valid
                     for archive members.  If _r_e_f is non-null, it must have
                     been created with the _EEEE_LLLL_FFFF______CCCC______RRRR_DDDD_WWWW_RRRR command.

     _EEEE_LLLL_FFFF______CCCC______WWWW_RRRR_IIII_TTTT_EEEE     If the program wishes to ignore previous file contents,
                     presumably to create a new file, it should set _c_m_d to
                     this value.  _r_e_f is ignored for this command.

     _EEEE_LLLL_FFFF______CCCC______WWWW_RRRR_IIII_TTTT_EEEE______FFFF_AAAA_SSSS_TTTT
                     is the same as _EEEE_LLLL_FFFF______CCCC______WWWW_RRRR_IIII_TTTT_EEEE except that instead of
                     _m_a_l_l_o_c()ing memory for the output file (and then doing a
                     _w_r_i_t_e(2) and _f_r_e_e()) _EEEE_LLLL_FFFF______CCCC______WWWW_RRRR_IIII_TTTT_EEEE______FFFF_AAAA_SSSS_TTTT writes the output
                     directly to the file system (by doing _w_r_i_t_es as needed).
                     Avoiding the _m_a_l_l_o_c() can help limit time-consuming
                     paging activity.

     _eeee_llll_ffff______bbbb_eeee_gggg_iiii_nnnn ``works'' on all files (including files with zero bytes),
     providing it can allocate memory for its internal structures and read any
     necessary information from the file.  Programs reading object files thus
     may call _eeee_llll_ffff______kkkk_iiii_nnnn_dddd or _eeee_llll_ffff______gggg_eeee_tttt_eeee_hhhh_dddd_rrrr to determine the file type (only object
     files have an ELF header).  If the file is an archive with no more
     members to process, or an error occurs, _eeee_llll_ffff______bbbb_eeee_gggg_iiii_nnnn returns a null pointer.
     Otherwise, the return value is a non-null ELF descriptor.

     Before the first call to _eeee_llll_ffff______bbbb_eeee_gggg_iiii_nnnn, a program must call _eeee_llll_ffff______vvvv_eeee_rrrr_ssss_iiii_oooo_nnnn to
     coordinate versions.

SSSSYYYYSSSSTTTTEEEEMMMM SSSSEEEERRRRVVVVIIIICCCCEEEESSSS
     When processing a file, the library decides when to read or write the
     file, depending on the program's requests.  Normally, the library assumes
     the file descriptor remains usable for the life of the ELF descriptor.
     If, however, a program must process many files simultaneously and the
     underlying operating system limits the number of open files, the program



                                                                        PPPPaaaaggggeeee 2222






EEEELLLLFFFF____BBBBEEEEGGGGIIIINNNN((((3333EEEE))))                                                    EEEELLLLFFFF____BBBBEEEEGGGGIIIINNNN((((3333EEEE))))



     can use _eeee_llll_ffff______cccc_nnnn_tttt_llll to let it reuse file descriptors.  After calling
     _eeee_llll_ffff______cccc_nnnn_tttt_llll with appropriate arguments, the program may close the file
     descriptor without interfering with the library.

     All data associated with an ELF descriptor remain allocated until _eeee_llll_ffff______eeee_nnnn_dddd
     terminates the descriptor's last activation.  After the descriptors have
     been terminated, the storage is released; attempting to reference such
     data gives undefined behavior.  Consequently, a program that deals with
     multiple input (or output) files must keep the ELF descriptors active
     until it finishes with them.

EEEEXXXXAAAAMMMMPPPPLLLLEEEESSSS
     A prototype for reading a file appears below.  If the file is a simple
     object file, the program executes the loop one time, receiving a null
     descriptor in the second iteration.  In this case, both _eeee_llll_ffff and _aaaa_rrrr_ffff will
     have the same value, the activation count will be two, and the program
     calls _eeee_llll_ffff______eeee_nnnn_dddd twice to terminate the descriptor.  If the file is an
     archive, the loop processes each archive member in turn, ignoring those
     that are not object files.

          _iiii_ffff _((((_eeee_llll_ffff______vvvv_eeee_rrrr_ssss_iiii_oooo_nnnn_((((_EEEE_VVVV______CCCC_UUUU_RRRR_RRRR_EEEE_NNNN_TTTT_)))) _====_==== _EEEE_VVVV______NNNN_OOOO_NNNN_EEEE_))))
          _{{{{
                  _////_**** _llll_iiii_bbbb_rrrr_aaaa_rrrr_yyyy _oooo_uuuu_tttt _oooo_ffff _dddd_aaaa_tttt_eeee _****_////
                  _////_**** _rrrr_eeee_cccc_oooo_vvvv_eeee_rrrr _ffff_rrrr_oooo_mmmm _eeee_rrrr_rrrr_oooo_rrrr _****_////
          _}}}}
          _cccc_mmmm_dddd _==== _EEEE_LLLL_FFFF______CCCC______RRRR_EEEE_AAAA_DDDD_;;;;
          _aaaa_rrrr_ffff _==== _eeee_llll_ffff______bbbb_eeee_gggg_iiii_nnnn_((((_ffff_iiii_llll_dddd_eeee_ssss_,,,, _cccc_mmmm_dddd_,,,, _((((_EEEE_llll_ffff _****_))))_0000_))))_;;;;
          _wwww_hhhh_iiii_llll_eeee _((((_((((_eeee_llll_ffff _==== _eeee_llll_ffff______bbbb_eeee_gggg_iiii_nnnn_((((_ffff_iiii_llll_dddd_eeee_ssss_,,,, _cccc_mmmm_dddd_,,,, _aaaa_rrrr_ffff_))))_)))) _!!!!_==== _0000_))))
          _{{{{
                  _iiii_ffff _((((_((((_eeee_hhhh_dddd_rrrr _==== _eeee_llll_ffff_3333_2222______gggg_eeee_tttt_eeee_hhhh_dddd_rrrr_((((_eeee_llll_ffff_))))_)))) _!!!!_==== _0000_))))
                  _{{{{
                          _////_**** _pppp_rrrr_oooo_cccc_eeee_ssss_ssss _tttt_hhhh_eeee _ffff_iiii_llll_eeee _...._...._.... _****_////
                  _}}}}
                  _cccc_mmmm_dddd _==== _eeee_llll_ffff______nnnn_eeee_xxxx_tttt_((((_eeee_llll_ffff_))))_;;;;
                  _eeee_llll_ffff______eeee_nnnn_dddd_((((_eeee_llll_ffff_))))_;;;;
          _}}}}
          _eeee_llll_ffff______eeee_nnnn_dddd_((((_aaaa_rrrr_ffff_))))_;;;;

     Alternatively, the next example illustrates random archive processing.
     After identifying the file as an archive, the program repeatedly
     processes archive members of interest.  For clarity, this example omits
     error checking and ignores simple object files.  Additionally, this
     fragment preserves the ELF descriptors for all archive members, because
     it does not call _eeee_llll_ffff______eeee_nnnn_dddd to terminate them.











                                                                        PPPPaaaaggggeeee 3333






EEEELLLLFFFF____BBBBEEEEGGGGIIIINNNN((((3333EEEE))))                                                    EEEELLLLFFFF____BBBBEEEEGGGGIIIINNNN((((3333EEEE))))



          _eeee_llll_ffff______vvvv_eeee_rrrr_ssss_iiii_oooo_nnnn_((((_EEEE_VVVV______CCCC_UUUU_RRRR_RRRR_EEEE_NNNN_TTTT_))))_;;;;
          _aaaa_rrrr_ffff _==== _eeee_llll_ffff______bbbb_eeee_gggg_iiii_nnnn_((((_ffff_iiii_llll_dddd_eeee_ssss_,,,, _EEEE_LLLL_FFFF______CCCC______RRRR_EEEE_AAAA_DDDD_,,,, _((((_EEEE_llll_ffff _****_))))_0000_))))_;;;;
          _iiii_ffff _((((_eeee_llll_ffff______kkkk_iiii_nnnn_dddd_((((_aaaa_rrrr_ffff_)))) _!!!!_==== _EEEE_LLLL_FFFF______KKKK______AAAA_RRRR_))))
          _{{{{
                  _////_**** _nnnn_oooo_tttt _aaaa_nnnn _aaaa_rrrr_cccc_hhhh_iiii_vvvv_eeee _****_////
          _}}}}
          _////_**** _iiii_nnnn_iiii_tttt_iiii_aaaa_llll _pppp_rrrr_oooo_cccc_eeee_ssss_ssss_iiii_nnnn_gggg _****_////
          _////_**** _ssss_eeee_tttt _oooo_ffff_ffff_ssss_eeee_tttt _==== _...._...._.... _ffff_oooo_rrrr _dddd_eeee_ssss_iiii_rrrr_eeee_dddd _mmmm_eeee_mmmm_bbbb_eeee_rrrr _hhhh_eeee_aaaa_dddd_eeee_rrrr _****_////
          _wwww_hhhh_iiii_llll_eeee _((((_eeee_llll_ffff______rrrr_aaaa_nnnn_dddd_((((_aaaa_rrrr_ffff_,,,, _oooo_ffff_ffff_ssss_eeee_tttt_)))) _====_==== _oooo_ffff_ffff_ssss_eeee_tttt_))))
          _{{{{
                  _iiii_ffff _((((_((((_eeee_llll_ffff _==== _eeee_llll_ffff______bbbb_eeee_gggg_iiii_nnnn_((((_ffff_iiii_llll_dddd_eeee_ssss_,,,, _EEEE_LLLL_FFFF______CCCC______RRRR_EEEE_AAAA_DDDD_,,,, _aaaa_rrrr_ffff_))))_)))) _====_==== _0000_))))
                          _bbbb_rrrr_eeee_aaaa_kkkk_;;;;
                  _iiii_ffff _((((_((((_eeee_hhhh_dddd_rrrr _==== _eeee_llll_ffff_3333_2222______gggg_eeee_tttt_eeee_hhhh_dddd_rrrr_((((_eeee_llll_ffff_))))_)))) _!!!!_==== _0000_))))
                  _{{{{
                          _////_**** _pppp_rrrr_oooo_cccc_eeee_ssss_ssss _aaaa_rrrr_cccc_hhhh_iiii_vvvv_eeee _mmmm_eeee_mmmm_bbbb_eeee_rrrr _...._...._.... _****_////
                  _}}}}
                  _////_**** _ssss_eeee_tttt _oooo_ffff_ffff_ssss_eeee_tttt _==== _...._...._.... _ffff_oooo_rrrr _dddd_eeee_ssss_iiii_rrrr_eeee_dddd _mmmm_eeee_mmmm_bbbb_eeee_rrrr _hhhh_eeee_aaaa_dddd_eeee_rrrr _****_////
          _}}}}

     The following outline shows how one might create a new ELF file.  This
     example is simplified to show the overall flow.

          _eeee_llll_ffff______vvvv_eeee_rrrr_ssss_iiii_oooo_nnnn_((((_EEEE_VVVV______CCCC_UUUU_RRRR_RRRR_EEEE_NNNN_TTTT_))))_;;;;
          _ffff_iiii_llll_dddd_eeee_ssss _==== _oooo_pppp_eeee_nnnn_((((_""""_pppp_aaaa_tttt_hhhh_////_nnnn_aaaa_mmmm_eeee_""""_,,,, _OOOO______RRRR_DDDD_WWWW_RRRR_||||_OOOO______TTTT_RRRR_UUUU_NNNN_CCCC_||||_OOOO______CCCC_RRRR_EEEE_AAAA_TTTT_,,,, _0000_6666_6666_6666_))))_;;;;
          _iiii_ffff _((((_((((_eeee_llll_ffff _==== _eeee_llll_ffff______bbbb_eeee_gggg_iiii_nnnn_((((_ffff_iiii_llll_dddd_eeee_ssss_,,,, _EEEE_LLLL_FFFF______CCCC______WWWW_RRRR_IIII_TTTT_EEEE_,,,, _((((_EEEE_llll_ffff _****_))))_0000_))))_)))) _====_==== _0000_))))
                  _rrrr_eeee_tttt_uuuu_rrrr_nnnn_;;;;
          _eeee_hhhh_dddd_rrrr _==== _eeee_llll_ffff_3333_2222______nnnn_eeee_wwww_eeee_hhhh_dddd_rrrr_((((_eeee_llll_ffff_))))_;;;;
          _pppp_hhhh_dddd_rrrr _==== _eeee_llll_ffff_3333_2222______nnnn_eeee_wwww_pppp_hhhh_dddd_rrrr_((((_eeee_llll_ffff_,,,, _cccc_oooo_uuuu_nnnn_tttt_))))_;;;;
          _ssss_cccc_nnnn _==== _eeee_llll_ffff______nnnn_eeee_wwww_ssss_cccc_nnnn_((((_eeee_llll_ffff_))))_;;;;
          _ssss_hhhh_dddd_rrrr _==== _eeee_llll_ffff_3333_2222______gggg_eeee_tttt_ssss_hhhh_dddd_rrrr_((((_ssss_cccc_nnnn_))))_;;;;
          _dddd_aaaa_tttt_aaaa _==== _eeee_llll_ffff______nnnn_eeee_wwww_dddd_aaaa_tttt_aaaa_((((_ssss_cccc_nnnn_))))_;;;;
          _eeee_llll_ffff______uuuu_pppp_dddd_aaaa_tttt_eeee_((((_eeee_llll_ffff_,,,, _EEEE_LLLL_FFFF______CCCC______WWWW_RRRR_IIII_TTTT_EEEE_))))_;;;;
          _eeee_llll_ffff______eeee_nnnn_dddd_((((_eeee_llll_ffff_))))_;;;;

     Finally, the following outline shows how one might update an existing ELF
     file.  Again, this example is simplified to show the overall flow.

          _eeee_llll_ffff______vvvv_eeee_rrrr_ssss_iiii_oooo_nnnn_((((_EEEE_VVVV______CCCC_UUUU_RRRR_RRRR_EEEE_NNNN_TTTT_))))_;;;;
          _ffff_iiii_llll_dddd_eeee_ssss _==== _oooo_pppp_eeee_nnnn_((((_""""_pppp_aaaa_tttt_hhhh_////_nnnn_aaaa_mmmm_eeee_""""_,,,, _OOOO______RRRR_DDDD_WWWW_RRRR_))))_;;;;
          _eeee_llll_ffff _==== _eeee_llll_ffff______bbbb_eeee_gggg_iiii_nnnn_((((_ffff_iiii_llll_dddd_eeee_ssss_,,,, _EEEE_LLLL_FFFF______CCCC______RRRR_DDDD_WWWW_RRRR_,,,, _((((_EEEE_llll_ffff _****_))))_0000_))))_;;;;

          _////_**** _aaaa_dddd_dddd _nnnn_eeee_wwww _oooo_rrrr _dddd_eeee_llll_eeee_tttt_eeee _oooo_llll_dddd _iiii_nnnn_ffff_oooo_rrrr_mmmm_aaaa_tttt_iiii_oooo_nnnn _...._...._.... _****_////

          _cccc_llll_oooo_ssss_eeee_((((_cccc_rrrr_eeee_aaaa_tttt_((((_""""_pppp_aaaa_tttt_hhhh_////_nnnn_aaaa_mmmm_eeee_""""_,,,, _0000_6666_6666_6666_))))_))))_;;;;
          _eeee_llll_ffff______uuuu_pppp_dddd_aaaa_tttt_eeee_((((_eeee_llll_ffff_,,,, _EEEE_LLLL_FFFF______CCCC______WWWW_RRRR_IIII_TTTT_EEEE_))))_;;;;
          _eeee_llll_ffff______eeee_nnnn_dddd_((((_eeee_llll_ffff_))))_;;;;

     In the example above, the call to _cccc_rrrr_eeee_aaaa_tttt truncates the file, thus ensuring
     the resulting file will have the ``right'' size.  Without truncation, the
     updated file might be as big as the original, even if information were
     deleted.  The library truncates the file, if it can, with _ffff_tttt_rrrr_uuuu_nnnn_cccc_aaaa_tttt_eeee [see
     _tttt_rrrr_uuuu_nnnn_cccc_aaaa_tttt_eeee(2)].  Some systems, however, do not support _ffff_tttt_rrrr_uuuu_nnnn_cccc_aaaa_tttt_eeee, and the



                                                                        PPPPaaaaggggeeee 4444






EEEELLLLFFFF____BBBBEEEEGGGGIIIINNNN((((3333EEEE))))                                                    EEEELLLLFFFF____BBBBEEEEGGGGIIIINNNN((((3333EEEE))))



     call to _cccc_rrrr_eeee_aaaa_tttt protects against this.

     Notice that both file creation examples open the file with write _a_n_d read
     permissions.  The library is not compiled to use _mmmm_mmmm_aaaa_pppp so there is no need
     for write permission. But for maximum portability with implementations
     that do use _mmmm_mmmm_aaaa_pppp for file creation you may wish to provide both write _a_n_d
     read permissions.

SSSSEEEEEEEE AAAALLLLSSSSOOOO
     _cccc_rrrr_eeee_aaaa_tttt(2), _llll_ssss_eeee_eeee_kkkk(2), _mmmm_mmmm_aaaa_pppp(2), _oooo_pppp_eeee_nnnn(2), _tttt_rrrr_uuuu_nnnn_cccc_aaaa_tttt_eeee(2), _eeee_llll_ffff(3E), _eeee_llll_ffff______cccc_nnnn_tttt_llll(3E),
     _eeee_llll_ffff______eeee_nnnn_dddd(3E), _eeee_llll_ffff______gggg_eeee_tttt_aaaa_rrrr_hhhh_dddd_rrrr(3E), _eeee_llll_ffff______gggg_eeee_tttt_bbbb_aaaa_ssss_eeee(3E), _eeee_llll_ffff______gggg_eeee_tttt_dddd_aaaa_tttt_aaaa(3E),
     _eeee_llll_ffff______gggg_eeee_tttt_eeee_hhhh_dddd_rrrr(3E), _eeee_llll_ffff______gggg_eeee_tttt_pppp_hhhh_dddd_rrrr(3E), _eeee_llll_ffff______gggg_eeee_tttt_ssss_cccc_nnnn(3E), _eeee_llll_ffff______kkkk_iiii_nnnn_dddd(3E),
     _eeee_llll_ffff______nnnn_eeee_xxxx_tttt(3E), _eeee_llll_ffff______rrrr_aaaa_nnnn_dddd(3E), _eeee_llll_ffff______rrrr_aaaa_wwww_ffff_iiii_llll_eeee(3E), _eeee_llll_ffff______uuuu_pppp_dddd_aaaa_tttt_eeee(3E),
     _eeee_llll_ffff______vvvv_eeee_rrrr_ssss_iiii_oooo_nnnn(3E), _aaaa_rrrr(4).

NNNNOOOOTTTTEEEESSSS
     COFF is an object file format that preceded ELF .  COFF object files
     cannot be used with this library.

     _EEEE_LLLL_FFFF______CCCC______RRRR_EEEE_AAAA_DDDD______MMMM_MMMM_AAAA_PPPP and _EEEE_LLLL_FFFF______CCCC______WWWW_RRRR_IIII_TTTT_EEEE______FFFF_AAAA_SSSS_TTTT are options specific to this
     implementation, not options which are generally available.


































                                                                        PPPPaaaaggggeeee 5555